feat: update for latest OpenShell with Helm chart and provider system#1
Merged
Conversation
…r system Modernize the deployment to use the official OpenShell Helm chart and provider-based credential management instead of manual TLS generation, DaemonSet supervisor installation, and raw K8s secret extraction. Changes: - deploy.sh: use Helm pkiInitJob for TLS, remove DaemonSet supervisor (Helm handles init-container sideloading), remove manual credential secrets, make images configurable with upstream defaults - setup-providers.sh: new script to register credentials via `openshell provider create` instead of storing them as K8s secrets - ocp-sandbox.sh: use --provider flags for credential injection, auto-detect registered providers, keep file uploads for ADC/GWS - Remove obsolete docs (openshift-deploy.md, agent-observability-spike.md, quay-pull-secret.yaml.template) - Update README, sandbox-CLAUDE.md, sandbox-harness.md for new workflow
The local Helm chart uses appVersion 0.0.0 as a dev placeholder, which causes ImagePullBackOff for certgen and supervisor images. Auto-resolve the latest release tag from GitHub when no GATEWAY_IMAGE_TAG is set. Also set supervisor.image.tag to match the gateway tag and enable allowUnauthenticatedUsers for single-user dev clusters where the Helm chart does not render the mTLS auth config section.
ADC secrets (client_secret, refresh_token) are stored as provider credentials and resolved by the proxy during OAuth token exchange. Non-secret fields are injected as literal env vars since they're read locally by Google's auth library. Atlassian credentials use base64-encoded literal env vars (Basic auth hides placeholders from the proxy). MCP config written via python3 to prevent JSON injection. Network policy splits Google endpoints: L7 with body rewrite on oauth2.googleapis.com only, plain L4 passthrough for Vertex AI streaming. Adds downloads.claude.ai for skill/plugin installs.
7 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Modernize the harness to use the official OpenShell Helm chart and provider-based credential management:
pkiInitJobfor TLS (no manual OpenSSL), supervisor sideloading via init-container (no DaemonSet), configurable images with upstream defaultsopenshell provider createinstead of raw K8s secrets--providerflags for credential injection, auto-detect registered providers, keep file uploads for ADC/GWSRemoved
openshift-deploy.md,agent-observability-spike.md,quay-pull-secret.yaml.templateUpdated
Test plan
deploy.shon OpenShift cluster — gateway comes up, certgen job completessetup-providers.shwith env vars set —openshell provider listshows providersocp-sandbox.sh --name test— sandbox starts with credentials availablegh auth status, Jira MCP query,gwsCLI all workverify-integrations.pypasses